

This section will look at the issues of setting up various configurations
based on the use of Ethernet III card or Acorn Access cards.

AUN/Level 4
===========

When an AUN Ethernet III card is placed into a machine the bulk of the
software is dormant on power up. This software consists of the following
modules:

     Ether3                  1.26
     InternetA               1.13
     NetMsgs                 0.02
     Net                     1.21
*    BootNet                 0.84

(Modules marked with * are active on power up)

The software is activated or "switched on" by the Bootnet module which
provides the * command:

*configure Bootnet On|Off

When Bootnet is configured on all the software modules on the card become
active.

The Internet module provides the communication centre which allows the
Ethernet card hardware to pass data to the computer. In order to ensure that
the software could be placed on a convenient sized ROM the Internet module
was "cut down" so that it only supported the features required by AUN. This
"cut down" Internet is named InternetA. As we shall see there are different
versions of the Internet module for different tasks.

AUN/Gateway
===========

It is often necessary to provide communication between two similar or
disparate networks. Under AUN this functionality is provided by the !Gateway
application which requires a different Internet module. It was decided that
there should be a clear differentiation between client stations and Gateway
stations and so the Gateway function is achieved by a software application;
!Gateway. This requires an enhanced version of the InternetA module;
InternetAG, to be present in the computer. In order to prevent a clash
between the the InternetA and the InternetAG modules it is necessary to
"switch off" the AUN client software (*Configure  Bootnet off) before
running the Gateway application. This results in the InternetAG module been
used instead of InternetA.

AUN/TCP/IP
==========

In an Internet site (such as Acorn) the client stations may require
access to both Internet and AUN services. Provided in the AUN Level 4
Fileserver pack is the !Bootnet application software for such a situation.
It is possible to achieve this level of connectivity by simply disabling the
AUN client software and running the !Internet and !Bootnet applications in
that order. The !Internet software provides a fully functioning version of
the Internet module called Internet. When this version of the software is
loaded it is not possible to use the !Gateway application, as this is
superseded by the gateway functionality provided by the Internet software.

Acorn Access
============

When an Acorn Access card is placed into a machine the Access software is
immediately activated on power up. This software consists of the following
modules:

*    Ether3                  1.26
*    InternetA               1.13
     NetMsgs                 0.02
     Net                     1.21
*    AccMsgs                 0.01
*    BootNet                 0.84
*    Freeway                 0.10
*    ShareFS                 2.23
*    ADFSFiler               0.69

(Modules marked with * are active on power up)

The presence of the InternetA module at power up normally renders the Acorn
Access card unsuitable for use in a Gateway computer or as a client in a
full Internet site. This is because the InternetA module is incompatible
with the other versions needed by !Gateway and !Internet. In order to
provide the necessary alternative the InternetA module needs to be unlinked
from the other software before it can be replaced. The links to the other
modules then need to be rebuilt. 

As you can imagine, this is a somewhat involved and convoluted process. The
remainder of this document describes this process and thus enables Acorn
Access cards to be used in these environments.

Acorn Access and TCP/IP.
========================

This is the most straight forward of the different scenarios to get working
successfully. It requires the building of a two stage boot sequence which
includes a file which is accessed before the desktop is active and a file
which is called when the desktop becomes active.

The information provided here assumes that the necessary changes to the
!Internet and !BootNet application have been implemented. If a !Boot file;
of type Desktop, already exists then rename it as Desktop.

Using !Edit create an Obey file which contains the following lines:

     RMKill InternetA
     RMkill Sharefs
     RMkill freeway
     RMkill AccMsgs
     Run ADFS::4.$.Apps.tcp_ip.!Internet.!Run
     RMReinit AccMSGS
     RMReinit Freeway
     RMReinit sharefs
     Run ADFS::4.$.Apps.tcp_ip.!BootNet.!Run
     Desktop -f ADFS::4.$.Desktop | Used if there is a Desktop file
     |Desktop | Used if there isn't a Desktop file.

Note:   The pathnames to the applications and files may vary according to
        the disc structure used. The order in which the modules are
        *RMREINITed is vital.

Save this file as !Boot and reset the machine.

Acorn Access and !Gateway.
==========================

A two stage boot sequence is required. The information provided here assumes
that the necessary changes to the !Internet and !BootNet application have
been implemented. If a !Boot file; of type Desktop, already exists then
rename it as Desktop.

Using !Edit create an Obey file which contains the following lines:

     RMKill Freeway
     RMkill Sharefs
     RMKill InternetA
     RMKill AccMsgs
     Desktop -f ADFS::4.$.Desktop

Note:   The pathname to the Desktop file may vary according to the disc
        structure used.

Save this file as !Boot.

Using !Edit create a file of type Desktop or alternatively add these lines
to the very start of an existing Desktop file:

     Run ADFS::4.$.Network.!GateWay
     RMReinit AccMsgs
     RMReinit sharefs
     RMReinit Freeway
     Run ADFS::4.$.Network.!Server | Optional
     Run ADFS::HardDisc4.$.Network.!AAServer | Optional
     Share ADFS::HardDisc4.$ HardDisc4 | Mandatory for each exported disc

Save this file as $.Desktop.

Note:

!Gateway:       This must be started after the desktop otherwise the gateway
                icon will not appear on the icon bar, although the gateway
                will function correctly.

!AAServer:      If this is required on the Gateway machine, as well as Acorn
                Access, then the reference to -readonly must be removed from
                the !AAServer.!Config. If this is not done then the error
                Bad parameters will occur and !AAServer will fail to start.

                This has the added side effect of the contents of the
                !Config file being passed straight to the command line where
                they are interpreted by Acorn Access. As a consequence they
                will appear as unprotected Access disc icons, thus
                preventing them from being accessed by !AAClient computers.

                If the !AAServer directory(ies) are exported from the
                desktop each time then the commands are correctly passed to
                the !AAServer and exported accordingly.

Share           This command is mandatory and is necessary for each of the 
                exported Access discs in order to remind ShareFS of its
                exports. Failure to do this will result in any saved
                exports remaining unavailable.




